Conversation
Generate structured rule files to help LLMs understand and recommend motion presets. Includes 15 pilot files across all 5 categories for format validation: - entrance: FadeIn, ArcIn, BounceIn - scroll: ParallaxScroll, FadeScroll, ArcScroll - ongoing: Pulse, Bounce, Spin - mouse: Tilt3DMouse, TrackMouse, BounceMouse - background-scroll: BgParallax, BgZoom, BgFade Each rule contains: synonyms, visual description, when to use/not use, TypeScript parameters with constraints, minimal examples, and related presets.
- Updated visual descriptions to use plain language, focusing on user experience rather than technical details. - Streamlined "When to Use" and "When NOT to Use" sections for clarity and brevity. - Enhanced examples to demonstrate meaningful differences in behavior. - Removed unnecessary technical jargon and emphasized user-centric language across multiple preset files.
- Add 5 category files (entrance.md, scroll.md, ongoing.md, mouse.md, background-scroll.md) with decision guides - Each preset now has tags and synonyms for better LLM intent matching - Simplified preset files to focus on visual description, parameters, examples - Added accessibility considerations section to category files - Added time units (ms) to all duration/delay parameters - Updated PLAN.md with new structure and guidelines
- Updated descriptions, tags, and synonyms across multiple preset files to ensure uniform formatting. - Enhanced readability by standardizing bullet points and spacing. - Improved accessibility considerations and decision guides in category files for better user guidance.
There was a problem hiding this comment.
@tombigel @ameerabuf I don't think there's any use for a rules file per effect. I don't think there's a use-case for asking a whole file for a specific effect.
IMO there should be a single file per feature (e.g. entrance, loop) with a comparison table of all effects in that category.
Perhaps we need another single file which allows to quickly review all possible categories.
I think we should delete the single preset files. I don't think anyone will be able to review and maintain those.
Also, let's rename ongoing -> loop and mouse -> pointer
…e of truth - Add power-controlled params notes to all presets (Entrance, Scroll, Ongoing, Mouse) - Update PLAN.md with complete power mappings for regeneration - Consolidate documentation structure with presets-reference.md
- Clarify that background scroll requires data-motion-part attributes - Note that these animate DOM elements via transforms, not CSS background-position - Add ImageParallax exception for regular img elements
…n tation plan - Refactor section headings for better readability across all preset files. - Standardize usage notes for when to use and not use each animation type. - Consolidate available presets information and enhance quick decision tables. - Update PLAN.md to reflect the current status and versioning of presets.
|
|
||
| ## Regeneration Steps | ||
|
|
||
| 1. Check Preset Registry in this file for active presets (skip REMOVED presets) |
There was a problem hiding this comment.
of course it is. the presets might change, it changed numerous times while writing this file. before generation make sure your internal list is synced with the actual
Co-authored-by: Yehonatan Daniv <maggotfish@gmail.com>
- Rewrite trigger mechanisms as preset categories (not triggers) - Remove background scroll section (not functional yet) - Remove Status column and deleted presets from registry tables - Clarify animation options vs preset parameters (duration/delay are config-level) - Fix intensity values to match actual code powermaps (ArcIn, SpinIn, TiltScroll, ongoing presets) - Remove power reference from intensity guide heading - Add conditions note for reduced motion in accessibility section - Rewrite combining animations as general rules about CSS property conflicts - Remove migration reference and merge data sources into regeneration steps - Clean up Bg* preset references, fix desktop-only claim for mouse presets - Trim parameter naming conventions to overloaded names only (direction) - Remove --motion-opacity (unused), update distance units documentation Co-authored-by: Cursor <cursoragent@cursor.com>
- Rename GrowIn to ExpandIn across all preset docs (aligned with src/library) - Remove duplicate ExpandIn section in presets-reference.md - Remove deleted background-scroll.md - Add registry verification as first regeneration step in PLAN.md - Regenerate all category docs from updated PLAN.md Co-authored-by: Cursor <cursoragent@cursor.com>
editd some of the descriptions to be more accurate
…e fixes - Add designer-approved descriptions as single source of truth in plan - Replace tone selection table with 8 atmosphere groups (designer content) - Replace use-case table with placement recommendations - Fix discrepancies from source: GlideIn angle, ArcScroll perspective, direction table - Expand cross-category parallels and overloaded direction table - Exclude CustomMouse, SpinMouse, BounceMouse from generated rules - Fix intensity values: ArcIn easing, FlipIn initialRotate - Regenerate all 5 files from cleaned plan Made-with: Cursor
| @@ -0,0 +1,365 @@ | |||
| --- | |||
| name: entrance-presets | |||
| description: Full parameter reference for entrance motion presets. Read when configuring FadeIn, ArcIn, BlurIn, BounceIn, CurveIn, DropIn, ExpandIn, FlipIn, FloatIn, FoldIn, GlideIn, RevealIn, ShapeIn, ShuttersIn, SlideIn, SpinIn, TiltIn, TurnIn, or WinkIn entrance animations. | |||
There was a problem hiding this comment.
The description is important for letting the LLM know when to use this rule (skill), sort of used like in SEO.
I think listing the preset names is not a good way to expose it.
I think it would be better to replace with descriptive text, like: "Use when applying time-based entrance effects. Can be triggered via viewport entrance, pointer/keyboard singular interactions like click/*up/*down/*enter/*leave." etc.
No description provided.